-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use live API on cloud.gov for parsing #90
Conversation
@@ -104,31 +104,35 @@ const createPatternPreviewComponent = ( | |||
? 'form-group-row field-selected' | |||
: 'form-group-row'; | |||
|
|||
const editButton = pattern.type === 'input' ? ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only show the edit button if it's an input, skip for purely presentational elements.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I updated to hide when there is no edit component for the pattern defined.
Parsing now fires for all pdfs using the cloud.gov parser instead of a hard-coded cache 🎉
There's a few hundred millisecond delay because the API server is making an external API call to guess the title and produce a description. A good next step would be to split parsing into one endpoint and title/description auto-suggest into another (parsing alone is v fast).
Works reasonably well for AL Name Change. Parsing API needs be tested against a variety of pdfs, there be dragons 🐉 🐲 etc...
Also, removed the input edit button non-input elements.