Skip to content

🎨 Hackathon Project: First playful One Record Editor πŸͺ„

License

Notifications You must be signed in to change notification settings

aloccid-iata/neoneplay

Β 
Β 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

40 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

✨ NE:ONE Play ✨

This is a Hackathon implementation of the NE:ONE Play One Record Editor. Due to the nature of this code being written in 28 hours it is not pretty and pretty buggy. Therefore, this code is to be used at your own Risk, this code is not being maintained. A maintained and production ready version is currently in the planning.

Watch the video

↑ Submission Video from Hackathon with Demo ↑

🏁 Getting Started

git clone https://github.com/aloccid-iata/neoneplay.git
cd neoneplay
npm i
npm run dev

Now connect to localhost:3000 and enter your One Record Object ID in the Search bar at the top.

The code was developed and tested (very limited testing πŸ˜…) using the Chrome Browser, therefore for the best experience use Chrome.

🚧 Known Issues

  • One Record Server has to have enabled CORS Headers
  • When using One Record Servers without token authentication you need to expand the card to load the data (fixing this should just be adding a dependency to the useEffect Effect Array)
  • Some Features only work after a HotReload, this can be done by just changing a random file (could be adding a semicolon) in the project and saving it (for example the arrow descriptors are only located correctly after a hot reload)
  • Patch (Change) Requests only work on text fields outside of embedded objects. After committing a patch request the change is only displayed on servers without tokens, while on a server with a token the change is made but not shown in the UI. (sometimes patches don't work, in the hackathon there was not enough time for debugging)

πŸ”Ž Quirks

In the Hackathon the One Record Servers had a Bearer Token for Security Reasons. To demonstrate the NE:ONE Play Editor we asked for multiple servers to show how it could work with multiple industry players. We were given multiple servers, with the quirk that they all used the same Bearer Token, therefore in the Code (Settings.js file) there is a globalToken which is the Token for all of the hackathon servers. In the Hackathon this token was always filled in by hand as it had a lifetime of one hour.

✨ Development by


If there are any questions, you are welcome to open an Issue, answers are not guaranteed. If you are interested in further exploring NE:ONE, NE:ONE Play or any other ONE Record related topics together, please feel free to contact Oliver Ditz ([email protected]) from the department of aviation logistics of the Fraunhofer IML.

About

🎨 Hackathon Project: First playful One Record Editor πŸͺ„

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • JavaScript 99.9%
  • CSS 0.1%