You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After #174 the builder creates build hashes again to quickly select all modules that were selected previously. It puts the link in the downloaded file.
Additionally we could use history.pushState and history.replaceState to live update the URL with the hash, by md5 hashing the array of selected modules on the client-side.
timwienk
changed the title
Use history.replaceState to change the URL when selecting modules
Use history.replaceState to change the URL when selecting modules in builder
Nov 12, 2014
If we md5-hash on client side how would we know if the that module-string already exists?
The app.post() is sending the file to client-side and I don't think/know that we can get the hash tag from there. Maybe a Request would be needed there? or what do you have in mind @arian ?
Yeah the hash will not be available to the server-side. You'd have to
include that in the request.
On Mon, Nov 17, 2014 at 3:30 PM, Sergio Crisostomo <[email protected]
wrote:
If we md5-hash on client side how would we know if the that module-string
already exists?
The app.post() is sending the file to client-side and I don't think/know
that we can get the hash tag from there. Maybe a Request would be needed
there? or what do you have in mind @arianhttps://github.com/arian ?
—
Reply to this email directly or view it on GitHub #183 (comment).
After #174 the builder creates build hashes again to quickly select all modules that were selected previously. It puts the link in the downloaded file.
Additionally we could use
history.pushState
andhistory.replaceState
to live update the URL with the hash, by md5 hashing the array of selected modules on the client-side.Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: