Okay can’t seem to locate whether we’ve fully written this up yet. I can do so tomorrow, but here’s the deal:
We have a current page written in vanilla, we need to migrate to Preact. They're entirely different parts of the codebase. Old JS section and new JS section.
We want to keep the existing functionality but do things via states on Preact instead of vanilla spaghetti code.
If you’re not familiar with Rails you could start by installing the app and trying to get it up and running.
I’ll follow up with more details for this and similar issues in morning. 😄
How’s it going, I'm a Adam, a Full-Stack Engineer, actively searching for work. I'm all about JavaScript. And Frontend but don't let that fool you - I've also got some serious Backend skills.
Location
City of Bath, UK 🇬🇧
Education
10 plus years* active enterprise development experience and a Fine art degree 🎨
If you need some help with tips Samual give me a shout. I'm not super involved in react, I have more experience in Vue with tsx or plain Angular, however if you get started I can mentor you on this project.
As a user, I will want additional filters to narrow things down in my search. e.g. #360, but we don't currently have a great base for adding to the valnilla page.
Technical details
Right now, all the code for search is in _algolia_search.html.erb basically it's inline on the search page.
We want to move it to app/javascript. Create a new component in the src file called SearchResults and add a new pack called SearchResults, and then add <%= javascript_pack_tag "SearchResults", defer: true %> to _algolia_search.html.erb
Feel free to ask me for clarification.
Definition of Done
The current functionality has been replicated in clean, tested Preact code.
Here you go Samuel. If you get playing with this and it's a bit too complicated or weird to get going with, let me know. I could find something more straightforward to hack on.
Okay can’t seem to locate whether we’ve fully written this up yet. I can do so tomorrow, but here’s the deal:
We have a current page written in vanilla, we need to migrate to Preact. They're entirely different parts of the codebase. Old JS section and new JS section.
We want to keep the existing functionality but do things via states on Preact instead of vanilla spaghetti code.
If you’re not familiar with Rails you could start by installing the app and trying to get it up and running.
I’ll follow up with more details for this and similar issues in morning. 😄
Sure. I'll go ahead to install and get the app up and running while waiting for more information about the issue.
I'll also try to spend the time to get familiar with the code base.
Thanks much.
If you need some help with tips Samual give me a shout. I'm not super involved in react, I have more experience in Vue with tsx or plain Angular, however if you get started I can mentor you on this project.
Sure, I'll make sure to reach out once I get started on the project. Thanks much.
Feature Request or Task
As a user, I will want additional filters to narrow things down in my search. e.g. #360, but we don't currently have a great base for adding to the valnilla page.
Technical details
Right now, all the code for search is in
_algolia_search.html.erbbasically it's inline on the search page.We want to move it to
app/javascript. Create a new component in thesrcfile calledSearchResultsand add a newpackcalledSearchResults, and then add<%= javascript_pack_tag "SearchResults", defer: true %>to_algolia_search.html.erbFeel free to ask me for clarification.
Definition of Done
The current functionality has been replicated in clean, tested Preact code.
Here you go Samuel. If you get playing with this and it's a bit too complicated or weird to get going with, let me know. I could find something more straightforward to hack on.
Sure, I'll jump on it and make sure to keep you updated with my progress.
Thanks much.