Skip to content
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

Routines table had some incorrect escaping and hard-coded HTML #360

Merged
merged 1 commit into from Mar 30, 2024

Conversation

finanalyst
Copy link
Collaborator

  • Some routine names, eg <?>, were not HTML escaped
  • The routines dataset was no generic enough
  • Dataset created in secondaries and used in tablemanager
  • Refactored secondaries and tablemanager plugins.

- Some routine names, eg `<?>`, were not HTML escaped
- The routines dataset was no generic enough
- Dataset created in *secondaries* and used in *tablemanager*
- Refactored secondaries and tablemanager plugins.
@finanalyst
Copy link
Collaborator Author

@dontlaugh The changes here are to make the data from the routines page available for an sqlite database.
But these changes include needed updates for main.
Compare new raku routines with the production routines tab. You will see that the first two entries in the docs.raku.org tab have blanks in top two slots. This is due to an escape error.

A PR to create sqlite text is next

@dontlaugh
Copy link
Collaborator

Looks good. I will deploy to prod this weekend

@finanalyst finanalyst merged commit 3f27363 into main Mar 30, 2024
1 check passed
@finanalyst finanalyst deleted the refactor_tablemanager_secondaries branch March 30, 2024 09:21
@dontlaugh
Copy link
Collaborator

This should be deployed now to prod.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants