so far we had only one conference to show in html5 client, the conference id was set through build process
through the new url scheme, the client can detect conference id from rest init call. so in urlprovider the hard coded conference id from build process must be removed but an fallback for development must be implemented. if conference id can not detected in production, a error page needs to be displayed: "could not find conference: javaland 2029"
so far we had only one conference to show in html5 client, the conference id was set through build process
through the new url scheme, the client can detect conference id from rest init call. so in urlprovider the hard coded conference id from build process must be removed but an fallback for development must be implemented. if conference id can not detected in production, a error page needs to be displayed: "could not find conference: javaland 2029"
http://herbstcampus.latest.dukecon.org/2016/ => make init call http://herbstcampus.latest.dukecon.org/2016/init.json => {id: "1234"} http://herbstcampus.latest.dukecon.org/rest/conferences/1234